Memory management method and apparatus for automated biological reaction system

ABSTRACT

A reagent management system for an automated biological reaction apparatus including an automated biological reaction apparatus including at least one reagent dispenser for applying a reagent to a sample, a memory device containing data for a reagent device selected from the group consisting of a reagent dispenser or a reagent kit used in the automated biological reaction apparatus, a host device comprising a processor and a host device memory connected to the processor, the host memory device including a reagent table, and a scanner for transferring the memory device data to the host device memory,

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of co-pending U.S. patent application Ser. No. 09/571,989, filed on May 16, 2000, which in turn is a divisional of U.S. patent application Ser. No. 09/469,601, filed on Dec. 21, 1999, now abandoned, which is a continuation of U.S. patent application Ser. No. 08/909335, filed on Aug. 11, 1997, now U.S. Pat. No. 6,093,574. The entire contents of these patents and patent applications, including the specifications, are incorporated herein by reference.

BACKGROUND OF THE INVENTION

A. Field of the Invention

This invention relates to biological reaction systems, and more particularly relates to a method and apparatus for an automated biological reaction system.

B. Description of Related Art

Immunostaining and in situ DNA analysis are useful tools in histological diagnosis and the study of tissue morphology. Immunostaining relies on the specific binding affinity of antibodies with epitopes in tissue samples, and the increasing availability of antibodies which bind specifically with unique epitopes present only in certain types of diseased cellular tissue. Immunostaining requires a series of treatment steps conducted on a tissue section mounted on a glass slide to highlight by selective staining certain morphological indicators of disease states. Typical steps include pretreatment of the tissue section to reduce non-specific binding, antibody treatment and incubation, enzyme labeled secondary antibody treatment and incubation, substrate reaction with the enzyme to produce a fluorophore or chromophore highlighting areas of the tissue section having epitopes binding with the antibody, counterstaining, and the like. Each of these steps is separated by multiple rinse steps to remove unreacted residual reagent from the prior step. Incubations are conducted at elevated temperatures, usually around 40° C., and the tissue must be continuously protected from dehydration. In situ DNA analysis relies upon the specific binding affinity of probes with unique nucleotide sequences in cell or tissue samples and similarly involves a series of process steps, with a variety of reagents and process temperature requirements.

Automated biological reaction systems include the biological reaction apparatus and the dispensers for the reagents and other fluids used in the biological reaction apparatus. As disclosed in U.S. Pat. No. 5,595,707, inventors Copeland et al., entitled Automated Biological Reaction Apparatus, assigned to Ventana Medical Systems, Inc. which is incorporated herein by reference, the biological reaction apparatus may be computer controlled. However, the computer control is limited in that it is dedicated to and resident on the biological reaction apparatus. Moreover, the memory, which is used in conjunction with the computer control, contains data relating to the reagents including serial number, product code (reagent type), package size (250 test), and the like.

One of the requirements in a biological reaction system is consistency in testing. In particular, the biological reaction system should apply a predetermined amount of fluid upon the slide in order to consistently test each slide in the automated biological reaction apparatus. Therefore, an important focus of a biological reaction system is to consistently and efficiently apply a predetermined amount of fluid on the slide.

Further, as disclosed in U.S. Pat. No. 5,232,664 entitled Liquid Dispenser by inventors Krawzak et al. and assigned to Ventana Medical Systems, Inc., which is incorporated herein by reference, reagents must be dispensed on the slide in precise amounts using a fluid dispenser. The fluid dispenser, which is used in conjunction with the biological reaction apparatus, should be easy to manufacture, reliable and compact in size.

In the processing of a biological reaction system, there is a need for consistently placing an amount of fluid on a slide. In order to accomplish this, reliable and accurate dispensers are necessary. U.S. Pat. Nos. 6,416,713, 6,192,945, and 6,045,759, the specifications of each of which are incorporated by reference, disclose dispensers that are associated with reagent containers for dispensing a known and reproducible amount of reagent onto a slide.

SUMMARY OF THE INVENTION

One aspect of this invention is a memory management system for an automated biological reaction apparatus. The memory management system includes a memory device, the memory device including a table containing data for a dispenser used in the automated biological reaction apparatus. The memory management system also including a means to transfer the data in the memory device to a host device. The host device comprises a processor and a host memory device connected to the processor. The host memory device includes a look-up table. The processor is connected, via the means to transfer the data in the memory device to a host device, to the memory device, and the processor updates the look-up table in the host memory device based on comparisons to the table in the memory device.

Another aspect of this invention is a method for updating dispenser information in an automated biological reaction system. The method includes the steps of providing a host device and a memory device, the host device comprising a processor, a host memory device connected to the processor, the host memory device including a look-up table, the memory device including a data storage device and expiration date information for the dispenser used in the automated biological reaction apparatus. The method also includes the step of reading by the host device of the barcode and expiration date information in the memory device. In addition, the method includes the step of updating the look-up table in the host device based on the barcode and expiration date information in the memory device. And, the method includes the step of writing in the memory device that the barcode and expiration date information has previously been read.

Yet another aspect of this invention is a method for programming a memory device for an automated biological reaction system. The method includes the step of selecting a form which includes information on numbers and types of dispensers in a kit for the automated biological reaction system. The method also includes the step of scanning in barcodes for a set of dispensers. Moreover, the method includes the step of determining the type of dispenser for each of the dispensers scanned in. Further, the method includes the step of comparing whether the numbers and types of dispensers scanned in correspond to the numbers and types of dispenser in the kit form. And, the method includes the step of programming the memory device if the numbers and types of dispensers scanned in equal the numbers and types of dispenser in the kit form.

These and other objects, features, and advantages of the present invention are discussed or apparent in the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

A presently preferred embodiment of the present invention is described herein with reference to the drawings wherein:

FIG. 1 is a left front, isometric view of the automated biological reaction system according to a first embodiment of this invention;

FIG. 2 is an exploded right front isometric view of the system shown in FIG. 1;

FIG. 3 is a partial exploded left front isometric view of the system shown in FIG. 1;

FIG. 4 is a partial exploded right rear isometric view of the apparatus shown in FIG. 1;

FIG. 5A is a block diagram of the modularity of the host and remote devices of the automated biological reaction system;

FIG. 5B is a format of the addressing for the host devices and remote devices described in FIG. 5A;

FIG. 5C is a communication transmission protocol between the host device and remote devices described in FIG. 5A;

FIG. 6A is an expanded block diagram of the remote device in FIG. 5A;

FIG. 6B is a circuit board connection diagram for the microcontroller;

FIGS. 7 and 8 illustrate the mounting of a fluid dispenser on a reagent tray and the manner in which a reagent tray is engaged with a drive carousel;

FIG. 9 is an exploded view of a prefilled fluid dispenser including a reagent memory device;

FIG. 10 is a block diagram of the manufacturer's system for programming an external memory device;

FIGS. 11A and B are flow charts for updating the master lot on the manufacturer's reagent database and for inputting data into a memory device;

FIG. 12 is a flow chart for downloading data from a memory device to the host system;

FIGS. 13A and B are flow charts for updating the memory devices of the user through information downloaded from an external memory device;

FIG. 14 is a flow chart for determining if the kit/dispensers for use by the operator are the correct number and correct complement;

FIGS. 15A-15G are flow charts of a preparation for a run using the dispense table; and

FIG. 16 is a flow chart of the testing run for the remote device.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The automated immunostaining system of this invention performs all steps of immunohistochemical staining irrespective of complexity or their order, at the time and temperature, and in the environment needed. Specially prepared slides containing a bar code identifier and a mounted tissue section are placed in special supports on a carousel, subjected to a preprogrammed sequence of reactions, and are removed from the carousel, ready for examination. For purposes of clarity of the following description of the apparatus of this invention and not by way of limitation, the apparatus will be described in terms of immunohistochemical processes.

FIG. 1 is front right isometric view of the automated biological reaction system with a host device 32 and one remote device 166. The remote device 166 includes a staining module 167, bulk fluid module 230 and the host device 32 includes a host computer 33, a monitor 34, a keyboard 35 and a mouse 37. FIG. 2 is a front right isometric view of the staining module which is part of the automated biological reaction system. Liquid and air supply tubing and electrical wiring connecting the respective components are conventional, well known in the art, and are omitted from the drawings for purposes of clarity.

The apparatus has an upper section 2, intermediate section 4 and lower section 6. In the upper section 2, reagent tray 10 which supports the reagent fluid dispensers 12 is mounted for rotation about its central axis 7 on reagent carousel 8. The reagent carousel 8 and slide carousel 24 are circular in the preferred embodiment, but can be any shape which allows integration with other components in the system. Reagent fluid dispensers 12, described herein with respect to FIGS. 10-21, required for the immunohistochemical reactions to be conducted during slide treatment cycle, are supported by the reagent tray 10 and mounted in reagent fluid dispenser receptors 11. These receptors 11 are configured to receive reagent fluid dispensers 12. The receptors 11 are preferably equally spaced in a circular pattern axially concentric with the carousel axis 7. The number of receptors 11 provided should be sufficient to accommodate the number of different reagent fluid dispensers 12 required for a cycle or series of cycles. Twenty-five fluid dispenser receptors 11 are shown, but the number can be smaller or greater, and the diameter of the reagent tray 10 can be increased to accept a larger number of reagent fluid dispensers 12. The reagent carousel 8 is rotated by the stepper motor 14 drive belt 16 to a position placing a selected reagent fluid dispenser 12 in the reagent deliver position under the air cylinder reagent delivery actuator over a slide to be treated with reagent.

The intermediate section 4 comprises a vortex mixing plate to which the 4 of the 6 mix blocks are attached, the remaining two mix blocks being mounted on the lower section. The lower section 6 comprises support plate 22 upon which the slide carousel 24 is rotatably mounted. The slide carousel 24 supports slide supports 26. Heated air is supplied to the apparatus via a resistive heating element and a blower. The heated air recirculates within the apparatus as shown in FIG. 3. The support plate 22 also supports a remote device microcontroller 36 on the automated biological reaction apparatus, power supply 24 and fluid and pneumatic valves 62. The remote device microcontroller printed circuit board 36, as described subsequently, is generally a processor and can be replaced by a standard computer. The remote device microcontroller printed circuit board 36 interfaces, via an RS-485 line, with a host device 32, as described subsequently in FIGS. 5A-5C. The lower section 6 includes support plate 40 upon which are supported accessories such as power supply 42 and buffer heater 44.

In the lower section 6, the stepper motor 48 rotates the slide carousel 24, engaging drive belt 25 engaging the drive sprocket of the slide carousel 24. The annular waste liquid sump surrounds the shroud and is supported on the bottom of plate 22. The waste reagent and rinse fluids are collected in the sump and passed to a drain through an outlet tube in the sump bottom (not shown).

Rinse and Liquid Coverslip™ (which is light oil substance used to prevent evaporation of the aqueous solutions on the slide) spray blocks 60 are supplied with fluid through conventional solenoid valves 62 (see also FIG. 6A, 248F-J). Buffer heater temperature sensor 66, mounted on buffer heater 44, controls the heat energy supplied to the buffer heater 44. Slide temperature monitoring sensor 68, mounted on support plate 22, controls the temperature of the air in the apparatus by controlling energy supplied to annular heater elements 27. Power supply 42 provides power to the stepper motors 14, 48 and control systems. FIG. 4 is a left front isometric view of the bulk fluid module system 230 which is included in the automated biological reaction system 150. The bulk fluid module 230 includes an air compressor 232, a pressure relief valve (prv) 238, cooling tubing 231, a water condenser and filter 234, an air pressure regulator 236, a bottle containing wash buffer 246, and a bottle containing Liquid Coverslip™ 244. The air compressor 232 provides compressed air which is regulated by the pressure relief valve (prv) 238 to 25 psi. The air passes from the compressor 232 through the cooling tubing and enters the condenser and filter 234. From the condenser and filter 234, the air passes to the pressure regulator 236. The pressure regulator 236 regulates the pressure to 13 psi. The air, maintained at 13 psi, is supplied to the wash buffer bottle 246 and the Liquid Coverslip™ bottle 244 and the staining module 167 (see FIG. 2). Water condensing out of the compressed air passes out of the condenser and filter through the pressure relief valve and exits the bulk module. Wash buffer and Liquid Coverslip™ are supplied to the staining module.

Referring to FIG. 5A, there is shown a block diagram of the automated biological reaction system 150. The automated biological reaction system 150 is segmented into a host device 32, which includes a typical personal computer, and at least one remote device 166, which includes the automated biological reaction device in FIGS. 2 and 6A. In the preferred embodiment, there are up to eight remote devices 166 which communicate with the host device 32. Each remote device 166 on the network has a unique address so that each remote device 166 may be identified and individually controlled by the host device 32. As described subsequently in FIG. 5B, the automated biological reaction system 150 can support up to eight remote devices 166 due to the 3 bits (values 0-7) dedicated to the addressing of the remote devices 166. A rotary switch is provided on the remote device 166 to allow for the identification and the changing of the 3 bit address for each remote device 166. All host messages include this address in them, as described subsequently in FIG. 5B. However, the number of remote devices 166 can be smaller or larger than eight, depending on the capacity requirements or practical limitations of the laboratory in terms of space. Moreover, the remote devices 166 may be immunohistochemistry staining modules, another type of instrument that performs a different type of staining, or another type of medical testing device.

Communication between the host device 32 and the remote devices 166 is accomplished using a serial RS-485 link, which serves as a network, that supports one host and up to 32 remotes at one time. In the preferred embodiment, addressing of the remote devices 166 allows up to 8 remote devices to communicate with the host at one time. The RS-485 link has at least two pairs of lines for communication, one pair for transmitting and one pair for receiving. The remote devices 166 which are connected to the network “hear” the host messages but do not “hear” other remote messages. In the preferred embodiment, all communications begin with a host message, followed a short time later by a response by a remote device 166 if present. If the host device 32 sends a message and there is no remote device 166 to respond to it, the host device 32 times out. In this manner, the communication provides a simple, collision-free link between the host device 32 and the remote devices 166. In an alternative embodiment, the remote devices 166, in addition to communicating with the host device 32, address each other. For example, the remote devices 166 address each other using the unique 3 bit address, sending information about staining runs, which are described subsequently.

As shown in FIG. 5A, the host device 32 is a typical personal computer with a processor 152 which includes a comparator 154 for comparing values in the processor. The processor 152 is also in communication with memory devices 156, including non-volatile memory devices such as a ROM 158, volatile memory devices such as a RAM 160, and a hard disk 162. Any of the memory devices may contain databases or look-up tables; however, in the preferred embodiment, the hard disk 162 contains the databases or look-up tables 164. The remote device 166 includes a processor, such as a microcontroller 36 wherein the microcontroller 36 has a comparator 170 for comparing values in the microcontroller 36. In an alternative embodiment, the microcontroller 36 in the remote device 166 is replaced by a personal computer. The microcontroller 36 is manufactured by Dallas Semiconductor, model number DS2251T 128K Soft microcontroller module. The microcontroller 36 has two lines (serial to PC, serial to next inst) to facilitate communication between the host and the remote devices. As shown in FIG. 5A, the host device 32, through the processor 152, is connected to the serial to PC pin of the microcontroller 36 of remote device 1 (166). The serial to next inst line of the microcontroller 36 of remote device 1 (166) is connected to the serial to PC pin of remote device 2 (166). The connections follow similarly through remote device N (166). In the preferred embodiment, there are up to 8 remote devices on the network. In order to terminate the network with the correct impedance in order to avoid any pulse reflections on the network, the serial to next instrument line is connected to a terminator 171. The terminator 171 can thereby match the impedance of the network. In the event that one of the remote devices on the network must be removed from the network, the serial to PC line and the serial to next remote device line need only be connected to each other for the remote device 166 to be removed from the network. Thereby, the network does not “see” that remote device 166 and is effectively removed from the network.

Referring to FIG. 5B, there is shown a format of the addressing for the host and remote devices 166 described in FIG. 5A. Both the host device 32 and the remote devices 166 have the same format and are distinguishable from one another only by the messages in their fields. Both the host device command and the remote device response for a given message transaction contains the same message. The first character is the start of message character. The 8^(th) bit is always set to 1, the lower 3 bits contain the address of the remote and bits 3-6 are unused. The host device 32 addresses the remote device 166 in this manner. The addressed remote responds in kind with its own address here.

The message length is 2 characters in length. This number indicates the number of characters in the entire message. This includes the start of message character and the message checksum character. This is the actual number of characters transmitted as seen through the host/remote serial ports. The message ID is one character in length. It tags a message with a number (0-255) that identifies it from other messages. The message ID provides identification for message acknowledges from the remote and provides safe message retry processing in the remote. The message ID is implemented by incrementing a number until it reaches 255, and thereafter returning to 0. Each successful message transmission causes the message ID to increment by 1. Retransmitted messages from the host, due to unsuccessful acknowledgments from the remote, are repeated with the same message ID as the original message. The message command is 1 character in length. For host messages, the message command indicates to the remote the type of command the message command data pertains to. For remote messages, this field is used to tell the host device 32 how the request was received. The message command data is of variable length. It contains additional message data, depending on the particular host command. The size of the message command data is dictated by the message length, described previously. After removing the other fields from around this field, the remainder is the message information. Since message commands may not require message command data, this field may not always be used. The message checksum is 1 character in length. It contains the computed checksum of all characters in the message, starting with the start of message character and including all message characters up to, but not including, this checksum field. No message is processed if the message checksum does not match the actual computed checksum of the received message.

Referring to FIG. 5C, there is shown a communication transmission protocol between the host device 32 and remote devices 166 described in FIG. 5A. Messages are downloaded from the host device 32 to the remote devices 166. The host device initiates a message to send to a remote device (172). The host device allocates memory to hold a message 176 and loads the message into memory 178. The host device 32 then places the message at the top or at the bottom of the queue 180, 182, depending on the priority of the message. Since the queue is first-in-first-out, the messages at the bottom of the queue go out first. Therefore, if a message must be sent out immediately, it is placed at the bottom of the queue 180. Otherwise, if it is a routine status message, the message is placed at the top of the queue 182. Thereafter, the messages are sent to the message queues for each of the up to eight remote devices 184, 186, 188, 190, 192, 194, 196, 198.

Ordinarily, when a message is sent from the host device 32 to a remote device 166, messages are sent periodically through the use of a timer. When the host device 32 determines that a message needs to be sent rapidly 174, the timer is turned off 200 and all of the messages from the specific queue as indicated by the host are sent 202. If the host device 32 determines that the message does not need to be rapidly sent, the message is sent in the predetermined sequence based on the timer by sending it in the predetermined sequence 206. The host uses the tab position 204, which indicates which remote to send the message to.

Referring to FIG. 6A, there is shown an expanded block diagram of the remote device 166. As discussed previously, the remote device 166 includes a microcontroller 36. The microcontroller 36 has a user switch and LEDs line which connects to the status PCB (printed circuit board) 294. The status PCB 294 is the interface to the user for the remote device 166 and includes three LEDs (light emitting diodes) for power determination, error notification and notification of a run in progress. The status PCB 294 also includes a switch 295, such as a push-button switch, which is used for testing of various functions. When the push-button switch 295 is depressed, the microcontroller 36 executes the last set of instructions (described later as macro 0) that was entered in the microcontroller 36. Macro 0, as described subsequently, is a list of instructions which are used to execute a staining run in the remote device 166. For testing purposes, operators may wish to review the last staining run. In order to do this without requiring the operator to download the program from the host device 32 to the remote device 166 (which may be in a different location), the operator may depress the push-button switch 295. In this manner, the operator may repeatedly execute the last run at the touch of a button.

The microcontroller 36 also has a slide fan out connection which is used to control the blower fan 4. The blower fan 4 recirculates air to heat the slides on the slide carousel 24 of the remote device 166 by forcing air over the heater 302 and then over the slides. The slide temp in connection on microcontroller 36 is connected to the slide temperature monitoring sensor 68 which senses the temperature of the air. The slide temperature monitoring sensor 68 is positioned in the path of the heated air and thereby sends information to the microcontroller 36 when to turn the slide heater 302 on and off. The slide heater out connection is connected to the slide heater 302 which, as discussed previously, heats the air in order to elevate the temperature of the slides. As discussed subsequently, the host device 32 downloads to the remote device 166 both the sequence of steps in a run program, and the sensor monitoring and control logic called the run rules. One of the environmental parameters is the upper and lower limit of the air temperature of the slides (used for heating the slides). If, during a run, the environmental temperature is below the lower limit, as indicated by slide temperature monitoring sensor 68, the slide heater 302 is turned on. Likewise, if the environmental temperature is above the upper limit, as indicated by slide temperature monitoring sensor 68, the slide heater 302 is turned off. The power supply 24 supplies both 24 VDC and 5 VDC to the applicable 24 VDC and 5 VDC connections. The 24 Volt power supply 24 is used to power the motors 14, 48 which move the slide carousel 24 and the reagent carousel 8, and the valves 248A-J, which are described subsequently. The 120 VAC input is sent through a power switch 310, a fuse 308 and a filter 306 to the AC In connection of the power supply 24. The 120 VAC input is also used to power the slide heater 302, buffer heater 44 and compressor 232 of the bulk fluid module, which are described subsequently. The serial to PC line and the serial to next remote device line are described with reference to FIG. 5A. The tub overflow in line receives input from a conductivity sensor 255 which senses the level of the waste in the tub 254. When the conductivity sensor 255 senses that the waste line is above a predetermined level, the conductivity sensor 255 notifies the microcontroller 36, which in turn sends a status message to the host device 32. The operator is first given an opportunity to clear the waste from the tub 254. If the tub 254 is still above the predetermined level, the run is stopped.

The buffer heater 44 is used to heat the wash buffer before it is placed on the slides since it has been determined that better results are achieved by heating the wash buffer to the temperature of the tissue on the slide. The buffer heater 44 consists of a cast aluminum block 250 with a spiral tubing 251 inside the block. When the wash buffer flows through the tubing 251 through the block 250, the temperature of the wash buffer will be the temperature of the aluminum block 250 upon exit from the tubing 251. In order to control the temperature of the block, a buffer heater temperature sensor 66 is used which is physically placed on the aluminum block 250. The microcontroller 36 receives the buffer temperature sensor input via the buffer temp line and can thereby control the temperature of the buffer heater 44 by turning on and off the buffer heater 44 via the buffer heater line on the PCB microcontroller 36.

The fluid valves 248A-J for the Liquid Coverslip™ and the wash buffer are controlled by the fluid valve connections. There is a separate pair of wires (power and ground) for each valve 248A-J shown in FIG. 6A which are omitted for ease of display. Each valve 248A-J is a relay which is activated by the microcontroller 36. Further, there is a slide door optical sensor 258 which is input to the slide door switch in line connection and which is used to determine if the front door 256 of the remote device 166 is open. This sensor 258 is used for safety reasons so that, if the front door is open and remains open for five minutes, the slide carousel 24 does not move. Moreover, there is a second optical sensor, the upper level optical sensor 262, which is used to determine if the upper chassis on the remote device 166 has been opened.

Further, as shown in FIG. 6A, the dispense cylinder 282 uses the dispense cylinder extend and the dispense cylinder retract so that the dispense plunger extends and retracts the fluid dispensers. Using air via the system air line, the dispense cylinder 282 is pushed out by using the dispense cylinder extend line. The microcontroller 36 controls the air valves 248A, 248B so that the relay corresponding to the dispense cylinder extend line is activated. In this manner, the dispense cylinder 282 pushes the fluid dispenser down, thereby dispensing reagent. In order to retract the dispense cylinder 282, the dispense cylinder retract valve 248B is activated using the system air line so that the fluid dispenser is pushed to retraction. Additionally, an extension spring is used to help speed the retraction process, as described subsequently. An optical sensor is used to determine if the dispense is extended, and thereby activated. When the dispense cylinder 282 is extended, the optical sensor is tripped validating that the dispense operation has occurred. Motors 14, 48 move the slide carousel 24 and the reagent carousel 8, and are connected to the slide motor out connection and the reagent motor out connection, respectively. The motors 14, 48 are typically stepper motors.

Sensors 274, 286 are placed in proximity to the slide carousel 24 and the reagent carousel 8 in order to determine the “home” position of each. In the case of the slide carousel 24, the slide carousel home sensor 274 is inductive-type and senses a piece of metal placed underneath the slide designated as the “home” position. When the “home” position is found, the sensor 274 sends a signal to the slide home in line of the microcontroller 36. In the case of the reagent tray 10, the sensor 286 also is an inductive-type of sensor. The reagent tray 10 has a large flat metal ring around the entire tray except for the home position. In this manner, when the sensor 286 senses an absence of metal, this is determined to be the home position thereby indicating to the microcontroller 36, via the reagent home in connection, that the home position is found. The sensor 286 senses the reagent tray 10, rather than the reagent carousel 8, since the user may remove the reagent tray 10. Additionally, since the sensor 286 looks for the absence of metal for the home position, the absence of the reagent tray 10 may be tested by looking for the absence of metal in two consecutive positions.

System pressure is determined via the system air line which directly feeds into a transducer 290. The transducer 290 generates an analog voltage which is proportional to the pressure. The output of the transducer 290 is then sent to an analog to digital converter (ADC) 292 whose output is sent to the microcontroller 36 via the system pressure in connection. Contrary to previous pressure switches which only indicated whether the pressure was below a minimum value, the transducer 290 and ADC 292 combination indicates to the microcontroller 36 the exact pressure. Therefore, the microcontroller 36 can determine both whether the pressure is too low and too high. In either instance, the microcontroller 36 sends an error message and shuts down the run.

As shown in FIG. 6A, the bulk fluid module 230 includes the compressor 232 which pressurizes the air to up to 90 psi. The compressed air is sent to a filter 234 in order to filter out water and other contaminants. Pressure is regulated in a two-step fashion. First, the pressure is regulated at the compressor to approximately 25 psi (±1 psi) via a spring diaphram (prv) 238. The prv 238 is manufactured by Norgren in Littleton, Colo., part number NIP-702 with a plastic bonnet. Second, the pressure is fine-tuned to 13 psi using an air pressure regulator 236. The pressure regulator 236 is very accurate in terms of precise pressure regulation over long periods of time. In this manner, the compressor 232 need not overwork itself since the prv 238 maintains the pressure at the output of the compressor to 25 psi by opening and letting out excess pressure when the pressure exceeds 25 psi. Water and particulates, which are filtered out of the air via the filter 234, are sent to a waste receptacle. The compressed air pressurizes the Liquid Coverslip™ and wash buffer bottles 244, 246 so that when the valves 248F-J are opened corresponding to the Liquid Coverslip™, volume adjust, dual rinse top, dual rinse bottom lines, the pressure is already on the line and the fluid may flow. In addition, the compressed air is used for the dispense cylinder extend line, the dispense cylinder retract line, the mirror air cylinder line, the vortex mixers line, and the bar code blowoff/airknife line. Filters 240 are used at the outputs of the Liquid Coverslip™ and wash buffer bottles 244, 246 in order to remove particulates which may get caught in the valves 248.

The mirror air cylinder line is used to turn the mirror cylinder 278 so that the bar code reader 276 either reads bar codes on the slides of the slide carousel 24 or bar codes on the fluid dispensers on the reagent carousel 8. The output from the bar code reader 276 is input to the microcontroller 36 via the bar code serial I/O connection. In between the valve 248C for the mirror air cylinder line and the mirror cylinder is a flow restrictor 268. The flow restrictor 268 slows the flow of air in the line while still maintaining the 13 psi pressure on the line. In this manner, this moves the mirror slower than would otherwise be done without the restrictor 268.

The vortex mixers 271 likewise operate off of the 13 psi system air line to mix the contents on the slide. The vortex mixers 271 may be used in a single stream or in a dual stream mode. In particular, a single stream of air or a dual stream of air may be used to mix the contents on the slide. Further, restrictors 268 are used in the vortex mixers lines in order to reduce the flow of air. In this manner, when the vortex mixers 271 are used to mix the contents on the slide, the fluid does not blow off the slide and the mixers do not dry any particular spot on the slide.

The bar code blowoff/airknife 267 is used to blow air on the portion of the slide which contains the bar code. In this manner, the bar code is easier to read. Further, fluid can be kept on the slide better due to surface tension if fluid near the edge of the slide is removed.

Referring to FIG. 6B, there is shown a circuit board connection diagram for the microcontroller. The sensors and motors for the remote device 166 plug into this board which in turn is in communication with the microcontroller.

FIGS. 7 and 8 illustrate the manner of mounting a fluid dispenser 400 in a reagent tray which is engaged in the reagent carousel 8. The foot 440 is initially inserted into a circular U-shaped groove 442 formed in the reagent tray 10. In an alternative embodiment, the foot is inserted into a rectangular shaped groove. Groove 444 of spring member 448 engages a circumferential lip 446 of the reagent tray 10. FIG. 7 shows a cross sectional view of the fluid dispenser 400 after it has been mounted on the reagent tray 10 showing in particular the manner in which foot 440 fits into groove 442 and showing the flexing of spring member 448 to hold the fluid dispenser 400 firmly in place. To remove the fluid dispenser 400, spring member 448 is simply bent inward slightly so that the groove 444 clears the lip 446, and the foot 440 is withdrawn from groove 442.

Referring to FIG. 9, there is shown an exploded view of a prefilled fluid dispenser with an evaporation ring 405 adjacent to the cap. A reagent memory device 784 (a barcode in this example) including information about the reagent container, is placed on the dispenser in order to be read by a corresponding memory device reader 276 (a bar code reader in this example). The dispenser label 786 is also placed on the dispenser.

Another aspect of this invention, is an apparatus and method to transfer data from the manufacturer to the customer. The manufacturer uses a manufacturing database in order to maintain a record of reagents, master lots, and serial numbers for kits and dispensers. The manufacturing database is preferably an Interbase (client/server) database contained in a single file. The manufacturing database definition consists of domains, tables, views, and triggers. Domains define the variable types and requirements used in tables. Tables define the data that is stored for each record. Views (meta-tables) are accessed as tables but do not contain data. The views collect data from tables. Triggers are programs that are executed on the Interbase server in response to defined events.

The database includes information about packages, kits and containers. The information is provided by one or more memory devices. In the case of a package, the information is provided by a touch memory device associated with the package. The touch memory device is generally “associated” with a package by attaching the touch memory device to the package. However, the touch memory device does not have to be attached to the package in order to be “associated” with the package. The touch memory device, could, for example be attached to an inventory that lists the package or it could be attached to the package bill of sale. In the case of a container, kit or dispenser, the information is provided by a reagent memory device that is “associated” with the container, dispenser or kit. The term “reagent vessel” will be used herein to refer collectively to any vessel that holds a reagent or solution useful in the automated systems of this invention including, but not limited to containers, bulk containers, dispensers, vials, and kits.

The memory devices may be selected from any devices that are capable of storing information about a reagent vessel and thereafter transmitting to and/or receiving information from a host computer. The memory device may be selected from linear barcodes, 2-dimensional barcodes, text read by OCR software, optical data matrices, such as Dataglyph®, RFID, or magnetic media such as a magnetic strip.

The memory device may be based upon RFID tag technology. RFID tags can be either active or passive. Passive RFID tags do not have their own power supply allowing the device to be quite small. Passive RFID tags are practically invisible and have practical read ranges that vary from about 10 mm up to about 5 meters.

Active RFID tags, on the other hand, must have a power source, and may have longer ranges and larger memories than passive tags, as well as the ability to store additional information sent by the transceiver. At present, the smallest active tags are about the size of a coin. Many active tags have practical ranges of tens of metres, and a battery life of up to several years.

There are four different kinds of RFID tags commonly in use. They are categorized by their radio frequency: Low frequency tags (between 125 to 134 kilohertz); High frequency tags (13.56 megahertz), UHF tags (868 to 956 megahertz), and Microwave RFID tags (2.45 gigahertz). UHF tags cannot be used globally as presently ther are no global regulations for their usage.

An RFID programming and/or scanning system may consist of several components: tags, tag readers, tag programming stations, circulation readers, sorting equipment, and tag inventory wands. The purpose of an RFID system is to enable data to be carried on or within a device and to be transmitted to or from a portable device, called a tag, which is read by an RFID reader and processed according to the needs of a particular application. The data transmitted by the tag may include identification or location information, or specifics about the tagged reagent device, such as type, date of manufacture, expiration date etc.

In a typical RFID system, individual objects are equipped with a small, inexpensive tag. The RFID tag contains a transponder with a digital memory chip that is given a unique electronic product code. The interrogator an antenna packaged with a transceiver and decoder, emits a signal activating the RFID tag so it can read and write data to it. When an RFID tag passes through the electromagnetic zone, it detects the reader's activation signal. The reader decodes the data encoded in the tag's integrated circuit (silicon chip) and thus the data is passed wirelessly to the host computer for processing. RFID tags and systems that are useful in this invention may be selected from TI-RFid_Systems manufactured by Texas Instruments and wireless RFID systems from InfoLogix, Hatboro, Pa. There are many other known manufacturers of RFID systems that alone or in combination can be used in the present application.

In one aspect of this invention information is stored on the database to define kits (which contain several dispensers) or single dispensers. Each reagent vessel, whether a kit including multiple dispensers, or a single dispenser, will include a reagent memory device. For purposes of describing this invention further, the reagent memory device will be described with reference to a barcode identifying the contents.

In the present invention, the reagent memory device (e.g., barcode) associated with kits will contain information such as the part number, master lot number and serial number. For single dispensers, the barcode memory device will contain information about the dispenser such as the part number, lot number and serial number. Serial numbers are assigned to kits sequentially for each master lot starting at 1 (i.e., the first kit created from each master lot will be assigned serial #1). The package barcodes are separate from the barcodes that appear on the individual dispensers within the package. In particular, in the case of a single dispenser package, the serial number on the package barcode label need not match the serial number of the single dispenser contained in the package.

The barcodes may be selected from one, two and three dimensional barcodes. For purposes of this description, the invention will be described with reference to one dimensional barcodes. The barcode is encoded with the Code 128 Symbology. Preferably, a plain text interpretation of the barcode appears as standard ASCII text below the barcode. This allows for operator verification of the data obtained by scanning. The fields on the package label will be fixed in length and combined into a single barcode by concatenation. For the dispensers, one of the fields is a product code (preferably 4 digits), which determines the contents of the dispenser, and another optional field is a serial number. The serial number is unique to the type of dispenser (i.e., the serial number for each dispenser of a certain type is incremented by one). By scanning the barcode fields, the device that programs the touch memory device, which is described subsequently, recognizes the type of dispenser. Moreover, the host device, which obtains the scanned information from the scanner (in this case a barcode reader) on the remote device, which is described subsequently, also determines the type of the dispenser based on the scanned barcode. For a barcode on a kit, one field will preferably correspond to a particular kit form, so that, when the kit barcode is scanned, the computer determines, through a look-up table, the particular kit form associated with the kit barcode, as described subsequently.

Referring to FIG. 10, there is shown a block diagram of the manufacturer's system for programming an external memory device. The manufacturing computer 500 is preferably a typical personal computer, with a processor 502 including a comparator 504, and memory 506 including RAM 508 and ROM 510. As described subsequently, the processor 502 is in communication with a scanner 512 and a memory device 516 such as an EPROM (erasable programmable read only memory). In the preferred embodiment, the processor 502 is in communication with the memory device 516 via a memory wand 514, as described subsequently.

The updating of the master lot and entering data into the memory device is shown in the flow chart in FIGS. 11A-11B. The master lot form supports functions such as assignment of master lot numbers to predefined kits, as well as lot numbers and expiration dates to each of the dispensers in the kit. The expiration date of the kit is the earliest of the expiration dates of the dispensers in that kit. If the operator wishes to update the master lot 570, the manufacturing database determines if the master lot is old or new 572. If new, the list of kits is displayed 574 and a blank template for the user selected kit 576. If old, the previous master lot is listed 578 and the user selected master lot is displayed 580. Data is entered for the master lot 582 and then saved 584.

Once the forms are set, the operator may begin to program the touch memory device 588. In one embodiment, the touch memory device 576 is an EPROM such as the Dallas Semiconductor DS1985 F5 16 Kbit add-only touch memory device. Other memory devices may be used to store the information and allow the end user to retrieve the information. For example, diskettes may be used as touch memory devices. Other memory devices such as linear barcodes, 2-dimensional barcodes, text read by OCR software, optical data matrices such as Dataglyph®, RFID, or magnetic media such as a magnetic strip all fall within the scope of the term “touch memory device” of this invention even though it is not necessary to touch the device in order to store date to or to retrieve data from many of the listed touch memory devices.

In an initial step, the package bar code labels are scanned 590. A Welsh Allyn Scanteam 5400/5700 hand held scanner is used. The scanner need only be configured once to identify the hardware platform and bar code symbology. The scanner is programmed to send a ‘!’ as a prefix character and also a ‘!’ as a suffix character. The prefix character is used to differentiate input from the scanner from input from the keyboard. The suffix character is used to identify completion of acquisition.

Based on the information scanned from the package, the kit type is determined from information in kit forms 592. In an alternative embodiment, the user is prompted to enter the type of kit. Based on this information, the computer determines the kit type.

The barcodes for each of the dispensers in the package is then scanned with a scanner 594. Information in the kit form is compared with the information scanned in 596. For example, the number of dispensers in the package is checked. If the number is too high or too low, the user is notified and the memory device is not programmed. Further, if the type of the dispensers in the package does not match the type of dispensers in the kit form, the user is notified and the memory device is not programmed. This is one of the methods to increase the quality control. If there was an error in the packaging of the package, (e.g., an incorrect dispenser was placed in the package), the user will be notified to correct the problem 598.

If the number and type of dispensers are correct, the database collects all data necessary for the current kit and dispensers 602. The touch memory data which includes information such as lot number, reagent type, expiration date, etc. is programmed into or stored into the touch memory device. Where the touch memory device is an EPROM, the data is programmed into the EPROM using object oriented programming. To do this, a touch memory object is created which contains the form in which the memory will be stored 604. The data for the current kit and dispensers is written to the touch memory object buffers 606. Finally, the touch memory object buffers are transferred to the touch memory device 608.

In order to program or read the EPROM the touch memory device, a probe (Dallas Semiconductor DS9092GT) mounted in a hand held wand 514 is used. This wand 514 is attached to the serial port of the manufacturing computer 500 programming the touch memory device 516 through a Dallas Semiconductor DS9097 or DS9097E serial port (DB-25) adapter. In an alternative embodiment that uses a diskette as a memory device, a disk drive is used to transfer the data on the memory device to the computer 500. When the touch memory device is an RFID tag, a RFID printer—encoder may be used that is attached to the manufacturing computer 500 may be used to program the RFID tag. One example of an RFID printer/encoder is a zebra RFID tag printer and coder model P104-000-PDE manufactured by Zebra Technology.

At the end user, the touch memory device accompanies the kit or single dispenser. Referring to FIG. 12, there is shown a flow chart for downloading data from a memory device to the host system. The probe is first connected to the touch memory device 612. The contents of the touch memory device are downloaded to the host computer 614 and displayed to the user 616. It is then determined whether the touch memory device has been downloaded previously 618. This is done based on the contents of the touch memory device. If the memory contents were previously downloaded, a flag is set in the memory contents. Therefore, this kit has already been “used” and therefore should not be reprocessed. The user is prompted whether he or she wants to update the user's databases with the kit/dispenser data 624. If so, the probe is reconnected to the touch memory device 626, verified that it is the same touch memory device by comparing the current downloading with the previous download of data 630. The flag indicating that the touch memory device is “used” is set inside the memory device 628. In this manner, a memory device may be downloaded only once for purposes of security. The contents of the user's databases are updated with information contained in the touch memory device such as name, type, group, lot, serial number, characteristics, quantity, expiration dates for the reagents, and the usable life, maximum volume, dead volume and registration date for the dispenser 632.

Regulations require that a user must maintain a database of the fluids used in staining. Prior to this invention, users were required to manually input data into the database. This process was not only time-consuming, but also prone to error. In contrast, the current invention uses information in the touch memory device to update the required database.

The user database, which is required by the regulations, contains various tables including the registration, receive and quality control tables for use by the operator. Within each of the registration, receive and quality control tables, there are five different types of categories: (1) antibodies; (2) reagents; (3) kits; (4) consumables, and (5) control slides. Antibodies are proteins having a specific affinity for a biological marker in a patient's tissue. Reagents are non-antibody chemicals that typically contain no living material. Kits, as described above, contain various combinations of dispensers. Consumables are materials such as the Liquid Coverslip™, wash buffer, etc. Each of these materials are regulated in different manners, thereby requiring different information contained within the registration, receive and quality control tables. For example, since antibodies are derived from living material, they are regulated more highly and therefore require additional information in the tables.

The registration table contains the background information for the specific material. For example, the registration table contains the name of the material (antibody, reagent, kit, consumable, or control slide), the manufacturer, the clone number (for antibodies) and other information describing the material. As described previously, one field in the dispenser barcode is the type of dispenser. This information is programmed into the touch memory device, which is subsequently downloaded to the registration table. Therefore, when the barcodes for the dispensers are scanned in preparation for a run, as described subsequently, the registration table is used to determine what type of fluid is contained in the dispenser. This table is updated only when the material is first received.

The receive table is a table which records each time when a certain material is received and the expiration date of that material as well as other information specific to this lot of material including the serial number. Therefore, while the registration table may describe the properties of a certain antibody, the receive table will describe on which dates each dispenser of that antibody was received, the expiration date for that antibody, the serial number and the lot number. This information is used not only to generate reports that are required by regulation, but also to check for the expiration date of the chemical during a run, which is described subsequently.

The quality control table records when a particular chemical was validated. Regulations require that when a new chemical or when a new lot for a previously received chemical is received, the lab must check to make sure the material performs in the expected manner (i.e., the material was processed correctly and not damaged in shipment). To determine if the material is “acceptable” to use in testing on patient tissue samples, end users have tissue samples that are known to test positive with undamaged reagents. The quality control table will track whether the chemical was tested for effectiveness and which tissue sample was used to test the chemical. In this manner, the tables, which are generated in large part by information from the touch memory, allow the end user to comply with the regulations without the need for time consuming data entry.

Other tables are used during a run which provide for better quality assurance in testing. For example, there is a dispenser table that contains, for each dispenser, the pertinent information for quality assurance during a run. For example, for each dispenser with a corresponding barcode (which contains the serial number for the dispenser), the table contains the expiration date, and the number of drops in the dispenser.

Referring to FIG. 13, there is shown a flow chart for updating the registration, receive and quality control tables on the host computer for use by the operator. Based on the data in the touch memory device, the computer determines whether the touch memory holds kit information, prefilled antibody information or prefilled reagent information. In particular, the computer may examine the format of the data in the touch memory device and determine what type of data the touch memory object holds. In the alternative, the touch memory device may specifically state whether the data relates to kit information, prefilled antibody information or prefilled reagent information. In particular, one of the fields in the touch memory device signifies what is the type of information.

Dispenser/kit information is read from the touch memory device. The computer determines if the touch memory device holds kit information 638. If so, the touch memory device searches the registration table to determine if the kit was previously received 640. If the kit was not received previously, the registration table must be updated with the kit registration information (i.e. background information) such as manufacturer and catalog number 642. This kit registration information is obtained from the touch memory device. The individual dispenser information within the kit, also obtained from the touch memory device, is updated in the dispenser table including the serial number, product code, master lot number, total dispenses (by number of drops) and expiration date 644.

The receive table is also updated to include the receive date, lot number, serial number, and receiver 646. The receive date is generated based on the date in the host device processor and the serial number is obtained from the touch memory device. The receiver field in the receive table is the person that has input the data from the touch memory device. In the preferred embodiment, the host device 32 determines who is currently logged on to the host device and writes the user's name as the receiver.

The quality control table is searched to determine if there is an entry in the table for this kit's lot number (i.e., if this is a new kit or a new kit lot number) 648. If the kit lot number (as obtained from the touch memory device) has already been quality control tested, the user is informed that this has already been done 650. If not, the user is informed that a quality control test must be performed 676. In an alternative embodiment, a separate look-up table is used to select known tissue samples to test the effectiveness of a received chemical received. Based on the chemical received, the known tissue samples are suggested to the user to test the effectiveness of the chemical in order to update the quality control table.

The computer may also determine if the touch memory device holds prefilled antibody information 652. If so, the touch memory device searches the registration table to determine if the antibody information was previously received 654. If the antibody information was not received previously, the registration table is updated with the antibody registration information (located in the touch memory device) such as name, manufacturer, catalog number, clone, Img subclass, presentation, and species 656. The individual dispenser information is also updated in the dispenser table including the serial number, product code, master lot number, total dispenses (by number of drops) and expiration date 658. The receive table is updated to include the receive date (as determined from the host device), lot number, serial number, and receiver 660. The quality control table is searched to determine if there is an entry in the table for this antibody lot number (i.e., if this is a new antibody or a new antibody lot number) 662. If the antibody lot number has already been quality control tested, the user is informed that this has already been done 650. If not, the user is informed that a quality control test must be performed 676.

The computer may also determine if the touch memory device holds prefilled reagent information 664. If so, the touch memory device searches the registration table to determine if the reagent information was previously received 666. If the reagent information was not received previously, the registration table is updated with the reagent registration information (located in the touch memory device) such as name, manufacturer, and catalog number 668. The individual dispenser information (located in the touch memory device) is updated in the dispenser table including the serial number, product code, master lot number, total dispenses (by number of drops) and expiration date 670. The receive table is updated with information from the touch memory device to include the receive date, lot number, serial number, and receiver 672. The quality control table is searched to determine if there is an entry in the table for this reagent lot number (i.e., if this is a new reagent or new reagent lot number) 674. If the reagent lot number has already been quality control tested, the user is informed that this has already been done 650. If not, the user is informed that a quality control test must be performed 676.

The computer may also determine if the touch memory device holds customer fillable dispenser information 678. If so, the individual dispenser information (located in the touch memory device) is input including the serial number, product code, master lot number, total dispenses, expiration date, dispenser drop life, maximum volume, dead volume and priming waste 680. In an alternative embodiment, the user is prompted to input the amount of liquid, in milliliters, which is placed in the dispenser. This amount in milliliters is converted into a number of drops and stored in the table. The user may, at a later time, fill the user fillable dispenser and, at that later time, update the dispenser table with the amount of fluid put in the dispenser.

In an alternative embodiment of the invention, the host device performs a series of checks using the information from the touch memory. Referring to FIG. 14, there is shown a flow chart for determining if the kit/dispensers for use by the operator is the correct number and correct complement, similar to the check performed while programming the touch memory device, as described in FIG. 11. The kit barcode information from the touch memory device is read to determine the type of kit and dispensers contained in the package 682, 684. Based on this barcode information, there is a look-up table which describes the number of reagents in the kit and the type or complement of reagents in the kit. This historical information in the look-up table is compared with what was actually sent in the package. If there is a discrepancy as to the number of dispensers in the kit or in the type of reagents in the kit 686, 688, the user is notified and the user's database is not updated with the kit barcode information 690. In this manner, checking whether the proper dispensers were included in the kit may increase the quality control.

After the downloading of the data from the touch memory device, the host device 32 and remote devices 166 may execute a run. As described previously, the host device 32 and remote devices 166 are modular in design. The host handles higher level system functions whereas the remote devices 166 perform the execution of the steps for staining. This modularity of design utilizing a personal computer as a host device 32 is beneficial in several respects. First, the host computer can be used to start runs on other remote devices 166. Second, the host device 32 can periodically update the software more efficiently on the remote device 166 based on upgrades in the operating system. For example, the lowest level code in the remote devices 166, which handles the basic input and output for the remote device 166 and the execution of programs, may be updated based on changes in error messaging, changes in output device design (such as different types of valves), and changes in the messaging protocols between the host and the remote. Third, the modularity multiplies the number of staining modules that may be run by a single machine. Fourth, since the host device 32 is comprised, in the preferred embodiment, of a personal computer, the host machine may be easily upwardly compatible, as opposed to previous standalone staining modules. Further, the personal computer can be integrated with a network environment to integrate with other computers. For example, there is a trend in hospitals to standardize the computer hardware used and to interconnect the computer hardware. The host device 32 may be connected to a hospital network, receiving commands from other computers on the network to execute a staining run, described subsequently, or sending results of a run to another computer on the network. Fifth, the host device 32 may serve as a platform through which various staining modules may be integrated. For example, there are various types of staining modules, some of which use dispensers versus vials, some of which use horizontal slide trays versus vertical slide trays, etc. The host device 32 may be integrated with a variety of staining modules, downloading programs to the different modules, described subsequently, depending on the particular configuration of the module. Sixth, the remote device 166, as a modular piece in the automated biological reaction system, may be serviced more easily. Instead of having a large machine dedicated to staining, the remote device 166 is smaller and can be shipped through the mail easily. In this manner, when an end user has difficulty with a remote device 166, the user may receive a second remote device through the mail, and send the faulty remote device back to be fixed. Therefore, the user need not rely on on-site maintenance for the remote device, and the attendant cost associated with on-site maintenance.

The host device may execute three different types of runs. The first run is a test run, which is described subsequently. The second run is a system run, whereby the remote device 166 reads the barcodes for the slides or the dispensers, or other non-staining functions required to setup a staining run. The third run is a staining run whereby the remote device 166 stains the slides. The second and third runs are described in FIG. 15. When executing a run, the host downloads a sequence of steps in a run program to the remote device 166. The run program is comprised of two separate pieces: (1) a main program (defined as macro 0); and (2) subroutines (defined as macros 1-255). The main program is composed of, but is not necessarily limited to, calls to the subroutines. Therefore, the entire length of the run program through calls to subroutines is less than a line by line execution of the entire program. For example, if a subroutine is called 50 times, the main program calls the subroutine 50 times rather than downloading a program which includes the code for the subroutine 50 times. In addition, the subroutines are defined by a programming language of thirty-one low-level commands which perform basic functions on the remote such as checking the timer, turning on an output such as a valve or a heater, or moving the carousel. When downloading the run program, the macros are downloaded as needed to execute a single run.

In addition to downloading a run program, the host device 32 downloads the sensor monitoring and control logic called the run rules. This program is made up of a series of continuous checks that must be done during the execution of the run program. As discussed previously, one of the checks is the upper and lower limit of the temperature of the slides. If, during a run, the environmental temperature is below the lower limit, as indicated by slide temperature monitoring sensor 68, the slide heater 302 is turned on. Likewise, if the environmental temperature is above the upper limit, as indicated by slide temperature monitoring sensor 68, the slide heater 302 is turned off. Another run rule relates to the opening of a system door. Additional run rules relate to the environment in which the remote device 166 executes the run. If any of the sensors are outside of the boundaries sent by the run rules, the remote device 166 sends a message which is retrieved by the host device 32. As discussed generally in FIG. 5C with respect to placing messages in the queue, the first priority is the execution of the steps in the run program. In addition to this, where spare processing is available, the host device 32 polls the remote device 166 for status. The host device 32 does this approximately every 1½ seconds to receive the status of the remote device 166 including the current temperature of the remote device 166, current step number being processed in the run program, elapsed time of the run, and any errors during the run. The host device 32 makes a record of any anomalies during the remote device run and prints the final report at the end of the run.

An example of a staining run is shown in flow chart form in FIG. 15. In preparation for a run, the operator determines the type of staining for the particular slides. Each slide has a barcode attached to it. Based on this barcode, the operator may program the type of staining. In order to assist the operator, the host device provides a set of recipes. For example, one test is a DAB paraffin test. Because this test is commonly used, the user may assign the barcode for the particular slide to that recipe thereby choosing the particular steps to perform the test. In addition, some of the recipes require the operator to enter certain parameters, called protocols. For example a protocol may be the specific temperature for the test or the time period for heating. In contrast to the protocols, the recipes define steps which the user does not control. For example, turning on valves, heating the slides, etc. are operations which the users cannot alter. In an alternative embodiment, each barcode on a slide may be standardized In order to simplify the procedure. For example, if the staining for the slide is to test for prostate cancer, a particular field within the barcode is placed on that slide which is used for every slide which is to be tested for prostate cancer. In that manner, the user is not required to enter a recipe for the particular slide, but rather the reading of the barcode determines the type of test.

After the operator has entered the recipes and protocols corresponding to each slide barcode for the staining run, step 695 in FIG. 15, the host device 32 may prepare for a staining run.

After the inputting of the recipes and the protocols, and prior to executing a run, the operator is prompted by the host device 32 (696). The host device first questions whether there is sufficient buffer solution in the wash buffer bottle 246, whether there is sufficient Liquid Coverslip™ in the Liquid Coverslip™ bottle 244, whether the level of waste in the waste tub 254 is acceptable, and whether the reagents and reagent tray 10 is loaded. The operator is then prompted for the number of slides that are loaded on the slide tray.

The first run is a system run to read the barcode on the slides. The operator then begins the run by downloading the file of steps to read the barcode on the slides and to wait for the host device 32 to retrieve the barcode 697. The remote device reads a barcode on the slide 698, stores the barcode in a file 699, to be used subsequently, then waits for the host device 32 to retrieve the barcode and retrigger the remote device 166 to read another barcode on the slide 700. The remote device 166 does this until the last slide is read 702.

The second run is another system run wherein the host device 32 downloads the run program and run rules in order to read the barcodes on the dispensers 704. Similar to the first system run, the remote device 166 reads a barcode on the dispenser 706, stores the barcode in a file 707 to be used subsequently, then waits for the host device 32 to retrieve the barcode and retrigger the remote device 166 to read another barcode on the dispenser 708. The remote device 166 does this until the last dispenser is read 710.

The host device 32 then reads the slide barcodes already stored in the file 712. If the number of entries in the file is different from the number previously entered by the operator (696), as performed in the loop at step 698, an error message is generated 730. This is done since the barcode reader, at times, may not read one of the barcodes on the slide. In that case, the run is stopped.

The host device 32 then reads the barcodes for the reagents already stored in the database 716. Based on the barcodes, the host device loads the protocols for the slides from the database. For each specific recipe, there are a series of macros which are to be executed by the remote device 166. In the case of a DAB paraffin test, a look-up table indicates the series of steps or macros. As discussed previously, there are macros from 1 to 255 which define basic operations of the remote device 166. For the specific task of a DAB paraffin test, the look-up table includes all the necessary macros, in the proper sequence, to perform the test. Based on these macros, the host device 32 determines the types of reagents and amount of drops required to execute the steps 714. Moreover, in creating the run program, calls to the macros are included in macro 0 and macros 1-255 which are to be called are included after macro 0. All the protocols for the particular recipes are loaded and determined if they exist in the database 718. Those protocols were previously entered at step 695. If so, the host device loads data from the dispense table 720 and determines if all of the dispensers are present and loaded 722. If so, the recipes are loaded from the database 724. The host device 32 then verifies that the recipes can be run together 726 (i.e., whether there are any procedures which are incompatible or unsynchronized). For example, if there are two recipes which dictate the temperature of the slides (where the slides are in close proximity), and the temperatures are different, the two recipes cannot be executed; therefore, an error message is generated 730. The steps for the run are then computed 728. Because there are several slides being tested, and each slide has a series of steps associated with it, the host device 32 generates the run program which can execute all the steps for all of the slides. The host device 32 is constrained by being able, for example, to mix with the vortex mixers 271 at a certain station on the slide carousel 24, to dual rinse at a certain station, to add fluid at the volume adjust, etc. Based on these constraints, the run program is generated which tells the remote to execute the steps in the proper sequence at the proper station 728.

The host device 32 determines if there are multiple dispensers of the same reagent 732. If so, an error message is generated since, for quality control purposes, dispensers from the same kit may only be used in a run. In addition, if a step requires applying two different reagents at the same station, the host device 32 requires that the reagents be next to each other. Otherwise, it would take too long to move the carousel and dispense both reagents. As a guideline, each step should be performed within 6 seconds in order to speed up the process of staining.

The host device 32 then determines if this is a titration run 734. In a user filled dispenser, the user may wish to test varying concentrations of reagent in the fluid dispenser. If so, the user executes a titration run whereby the user is allowed, via the program, to stop the run in the middle and titrate different concentrations. The amount of time for the titrations must be short enough so that the slide will not dry out 736. Otherwise, an error message is generated 750. The macro functions are loaded from a database for the run 738 and determined if all the macro functions loaded properly 740. The host device 32 determines, based on the dispenser table, whether any of the dispensers are past the expiration date 742. If so, the operator is notified 744. Similarly, the dispenser table is checked to determine if the dispensers have sufficient fluid to conduct the run 746. If not, the operator is notified to refill or replace the dispensers 748. Optionally, quality control can be checked to determine if all of the dispensers have been tested under quality control protocols 752.

Therefore, the host device 32 looks up in the dispenser table 716, described in FIG. 13, to determine if the reagents necessary (1) are past their expiration date; (2) are present to perform the run; (3) have enough drops in the dispensers to execute the run; or, optionally, (4) have been tested for quality control. If any of the first three conditions fail, the run cannot be executed and the operator is notified (i.e., one of the dispensers is past its expiration date, one of the dispensers is missing, or one of the dispensers is low on fluid).

Optionally, for quality control purposes, the dispenser table is searched to determine if quality control was performed on the dispenser 752. If it has not yet performed, the operator is notified 754 and asked if he or she wishes to proceed 756. If the operator wishes to proceed, he or she must enter his or her name, and the date and time in order to continue the run 758. Finally, when the run is executed, the information entered by the operator is included in the history of the run, described previously, to indicate that at least one of the dispensers had not been tested in compliance with the regulations, but that the run was performed anyway 760. In this manner, the quality of the run may be increased due to monitoring of the dispensers used in the testing of the tissue samples. The host device 32 then saves the dispense data for the run to a database 762 and merges the run rules, which determine the operating environment of the run, together for the run 764. The host device 32 downloads the run program and the run rules for the current staining procedure 766. The host device 32 commands the remote to run the steps and to run the checks or the run rules 768. The host device 32 then updates the tables based on the execution of the run. For example, the host device 32 decrements the number of drops in the dispenser table for each of the dispensers used in the run 769. As discussed previously, the host device 32 periodically checks the status of the remote device 770. After the remote device 166 finishes execution of the run program 772, the host device 32 compiles the history of the run and stores the information sent from the remote 774.

The host device 32 also communicates with the remote devices 166 by reading and writing information regarding the operation of the remote devices 166. For example, the host device 32 downloads a command indicating to the remote device the amount of time (in 10's of milliseconds) the valve 248G for the volume adjust line is on. This value is stored in non-volatile RAM on the remote device 166. Further, the host device 32 may poll the remote device 166 to send its stored value for the volume adjust time stored in non-volatile RAM. Other information, such as the slide temperature monitoring sensor 68, buffer heater temperature sensor 66 and system pressure transducer 290, as described in FIG. 6A, may be read by the host device 32 and may be calibrated by the host device 32. When reading the sensor information from the remote device 166, the calibration data is sent back to the host. Calibration data is used to adjust for constant errors inherent in each temperature sensor and pressure transducer. In order to correct for errors, the host device 32 writes to the remote device 166. For example, when calibrating the pressure sensor, the host device 32 commands the remote device 166 to perform span calibration of the system pressure transducer 290 at the preset pressure of 13.0 psi. The remote device 166 registers the current raw pressure as the 13.0 psi analog to digital point.

Referring to FIG. 16, there is shown a flow chart of the testing run for the remote device. One of the commands or steps downloaded to the remote device is a test command 776. The remote processes the commands in the run program 778 until the remote device 166 receives the test command 780. The remote device 166 then waits until a button 295 is pressed on the remote device 782, as described in reference to FIG. 6A. When the button 295 is pressed, the remote device 166 re-executes the run program, and then waits for the button 295 to be depressed again. In this manner, the operator may test individual steps or commands by pressing the button 295 and re-executing the previous set of commands. In an alternative embodiment, the remote device 166 interprets the test mode as a means by which to single step through the program. Every time the button 295 is pressed, the remote device 166 executes a command. In this manner, the operator may step through the run program and determine if there are any errors in the sequence of steps.

From the foregoing detailed description, it will be appreciated that numerous changes and modifications can be made to the aspects of the invention without departure from the true spirit and scope of the invention. This true spirit and scope of the invention is defined by the appended claims, to be interpreted in light of the foregoing specification. 

1. A reagent management system for an automated biological reaction apparatus comprising: an automated biological reaction apparatus including at least one container for holding a reagent for later application to a sample; a memory device containing data characteristic of said reagent in said container used in the automated biological reaction apparatus; a host device comprising a processor and a host device memory connected to the processor, the host memory device including a reagent table; a scanner for transferring the memory device data characteristic of said reagent to the host device memory.
 2. The reagent management system of claim 1 wherein the memory device is selected from the group consisting of linear barcodes, 2-dimensional barcodes, text, optical data matrices, RFID, magnetic media, and any combinations thereof.
 3. The reagent management system of claim 2 wherein the memory device is associated with a kit, dispenser or container.
 4. The reagent management system of claim 2 wherein the memory device is a touch memory device associated with a reagent vessel package.
 5. The reagent management system of claim 3 wherein the scanner is a bar code scanner.
 6. The reagent management system of claim 3 wherein the memory device is an RFID tag.
 7. The reagent management system of claim 6 wherein the scanner is an RFID tag reader.
 8. The reagent management system of claim 2 wherein the memory device is text and the scanner is a text scanner.
 9. The reagent management system of claim 1 wherein the reagent container is a reagent dispenser and wherein the reagent dispenser data includes an expiration date for the reagent.
 10. The reagent management system of claim 1 wherein the host device processor updates the reagent table in the host memory device based on comparisons to the reagent memory device table.
 11. The reagent management system of claim 10 including a means for checking whether the reagent memory device has been previously read prior to transfer to the host device of the data in the memory device.
 12. The reagent management system of claim 1 including a means for connecting the host computer processor to the memory device prior to scanning the data in the memory device.
 13. The reagent management system of claim 1 wherein the reagent device data includes a machine readable identifier for the reagent device.
 14. The system as claimed in claim 13 wherein the machine readable identifier comprises a reagent serial number and product code.
 14. A reagent management system comprising; an automated biological reaction apparatus including at least one container for holding a reagent for later application of said reagent to a sample undergoing a reaction in the automated biological reaction apparatus; a reagent vessel package containing the at least one reagent container; an RFID tag associated with at least one reagent vessel package, the RFID tag including data for characterizing said reagent used in the automated biological reaction apparatus; a host device comprising a processor and a host memory device connected to the processor, the host memory device including a reagent table; an RFID scanner for reading and transferring the characterizing data in the RFID tag to the host memory device; and means to write to the RFID tag that the characterizing data has been transferred, wherein the host device processor is connected to the RFID scanner.
 16. The reagent management system of claim 15 including a means for updating the reagent table in the host memory device when the characterizing data is transferred to the host memory device.
 17. The reagent management system of claim 15 wherein the characterizing data includes a machine readable identifier and expiration date information for the reagent.
 18. The reagent management system of claim 17 including a means for writing in the host memory device that the machine readable identifier and expiration date information has been read.
 19. The reagent management system of claim 18 wherein the means of writing in the host memory device includes setting a flag in the memory device. 